WA-NEW-011: Remove use_dis_max from query_string queries (ES7 compatibility)#634
WA-NEW-011: Remove use_dis_max from query_string queries (ES7 compatibility)#634kitcommerce wants to merge 1 commit intonextfrom
Conversation
Dispatcher Build Gate Summary (local)
Note: test output still prints BSON Symbol deprecation warning (expected to be addressed by WA-NEW-010 / PR #635). |
Security ReviewVerdict: APPROVE (low risk) SummaryThis PR removes Notes
|
Architecture ReviewVerdict: APPROVE (high confidence) SummaryMinimal, correct ES7 compatibility change: Notes
Optional test ideas
|
Simplicity ReviewVerdict: APPROVE (high confidence) SummarySmallest, clearest ES7 compatibility fix: remove unsupported Note (optional)
|
Rails / Workarea Conventions ReviewVerdict: APPROVE SummaryConventions-friendly, minimal change confined to query building: removes ES7-unsupported Notes / watch-outs (non-blocking)
Suggested follow-ups
|
✅ Wave 1 Passed — Merge ReadyWave 1 reviewers all returned APPROVE:
Build gate: Labeling this PR |
Summary
Remove the deprecated
use_dis_maxoption fromquery_stringqueries inProductSearchandHelpSearch. This option was removed in Elasticsearch 7 and causes a 400parsing_exception.Closes #628
Client impact
None expected.
use_dis_maxwas already the default behavior in ES5/6; removing it explicitly is a no-op for query semantics. Thetie_breakerparameter (which replaces the dis_max behavior) is retained.Verify